-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: reinstate tests #135
fix: reinstate tests #135
Conversation
first run: https://github.com/uc-cdis/WebAPI/actions/runs/8928129787/job/24522987771
second run: https://github.com/uc-cdis/WebAPI/actions/runs/8928129787/job/24524131137
third run: https://github.com/uc-cdis/WebAPI/actions/runs/8928129787/job/24525468942
thought: if the same 4 tests always fail, why not start skipping them for now instead of disabling all 220? 🤔 |
8b49e90
to
707b173
Compare
This allows the other tests to be reinstated while these two can then be fixed separately.
This allows the other tests to be reinstated while these two can then be fixed separately.
...this one seems to only work depending on the order of execution... it lacks the setup() method where a pre-filled db is guaranteed, like for example in CohortCharacterizationServiceTest
replaced by OHDSI#2368 which was merged into our local branch |
Reinstate tests, rolling back what was done in OHDSI#1903
Upstream PR: OHDSI#2368